Repository navigation
feat(website): ✨ read the versions and their dates from npm - #75
Merged
Merged
Conversation
The website had the versions written by hand: `@beta` in the menu and the install commands, 2.0.0-beta.0 in the header, the changelog and the structured data, while the release came out as 2.0.0-beta.1. Each release, and 2.0 going stable, meant editing them. The site now reads npm when it builds (vite.config.ts defines what src/data/npm.ts reads: the dist-tags and the day of each version), and src/data/release.ts names each major from it: its dist-tag while only prereleases are out (`@beta`, `@rc`), `@2` once stable, installed as plain `qwik-date` when `latest` is the newest major. The version menu, the install command and its "keep @beta" note, the compatibility table, the link from the 1.x docs and the version in the structured data follow; the changelog's sections take their newest version, its tag and its day (or "unreleased"), and list the ones before. Offline, a local build shows the repo's version as unreleased; in the CI it fails instead. llms.txt and llms-full.txt come from templates too (scripts/llms.md and llms-full.md, written by scripts/llms.ts, which `pnpm build.website` now runs first), so they leave the repo.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The website had the versions written by hand:
@betain the menu andthe install commands, 2.0.0-beta.0 in the header, the changelog and the
structured data, while the release came out as 2.0.0-beta.1. Each
release, and 2.0 going stable, meant editing them.
The site now reads npm when it builds (vite.config.ts defines what
src/data/npm.ts reads: the dist-tags and the day of each version), and
src/data/release.ts names each major from it: its dist-tag while only
prereleases are out (
@beta,@rc),@2once stable, installed asplain
qwik-datewhenlatestis the newest major. The version menu,the install command and its "keep @beta" note, the compatibility table,
the link from the 1.x docs and the version in the structured data
follow; the changelog's sections take their newest version, its tag
and its day (or "unreleased"), and list the ones before. Offline, a
local build shows the repo's version as unreleased; in the CI it fails
instead.
llms.txt and llms-full.txt come from templates too (scripts/llms.md and
llms-full.md, written by scripts/llms.ts, which
pnpm build.websitenowruns first), so they leave the repo.
Stack created with GitHub Stacks CLI • Give Feedback 💬